摘要 :
This paper presents our experiences in a project of a software engineering team spread across three countries that successfully established continuous delivery, DevOps and short release cycles with agile scrum. We had the challeng...
展开
This paper presents our experiences in a project of a software engineering team spread across three countries that successfully established continuous delivery, DevOps and short release cycles with agile scrum. We had the challenge to find a way from established regulatory heavy-weight processes, long release strategies, legacy tools and technologies and people mindset towards adopting continuous delivery and DevOps. We are describing our experiences in the journey towards timeboxed release strategies compared to legacy fixed scope-based releases; value stream-based execution compared to traditional milestone-based execution; operation, test, and infrastructure as a code compared to executing these activities manually. This paper also describes experiences in transforming traditional scrum team into a DevOps team, technological landscape into lightweight tools. The authors bring their experiences as a Project Manager, Quality Manager, and an Architect, who has been an integral part of this journey. These practices have helped in stabilizing processes and methods to an extent where we have released several products versions within a year. The other business units are adopting our practices for continuous delivery and DevOps. This paper also summaries our lessons learned, and recommendations.
收起
摘要 :
This paper presents our experiences in a project of a software engineering team spread across three countries that successfully established continuous delivery, DevOps and short release cycles with agile scrum. We had the challeng...
展开
This paper presents our experiences in a project of a software engineering team spread across three countries that successfully established continuous delivery, DevOps and short release cycles with agile scrum. We had the challenge to find a way from established regulatory heavy-weight processes, long release strategies, legacy tools and technologies and people mindset towards adopting continuous delivery and DevOps. We are describing our experiences in the journey towards timeboxed release strategies compared to legacy fixed scope-based releases; value stream-based execution compared to traditional milestone-based execution; operation, test, and infrastructure as a code compared to executing these activities manually. This paper also describes experiences in transforming traditional scrum team into a DevOps team, technological landscape into lightweight tools. The authors bring their experiences as a Project Manager, Quality Manager, and an Architect, who has been an integral part of this journey. These practices have helped in stabilizing processes and methods to an extent where we have released several products versions within a year. The other business units are adopting our practices for continuous delivery and DevOps. This paper also summaries our lessons learned, and recommendations.
收起
摘要 :
We introduced Product Line Engineering (PLE) with the objectives of 1) achieving shorter release cycles, 2) improving product quality, and 3) increasing cost-effectiveness. This paper shares our experiences in adopting PLE, descri...
展开
We introduced Product Line Engineering (PLE) with the objectives of 1) achieving shorter release cycles, 2) improving product quality, and 3) increasing cost-effectiveness. This paper shares our experiences in adopting PLE, describing the challenges faced in fulfilling these objectives. It also outlines the approaches that were used to overcome the architectural constraints, foster a culture of reuse, and enhance test automation. The resulting changes in team dynamics of globally distributed teams are also mentioned. We present the results and the extent to which the objectives were met. Finally, few challenges still faced by teams to move to shorter release cycle are highlighted.
收起
摘要 :
We introduced Product Line Engineering (PLE) with the objectives of 1) achieving shorter release cycles, 2) improving product quality, and 3) increasing cost-effectiveness. This paper shares our experiences in adopting PLE, descri...
展开
We introduced Product Line Engineering (PLE) with the objectives of 1) achieving shorter release cycles, 2) improving product quality, and 3) increasing cost-effectiveness. This paper shares our experiences in adopting PLE, describing the challenges faced in fulfilling these objectives. It also outlines the approaches that were used to overcome the architectural constraints, foster a culture of reuse, and enhance test automation. The resulting changes in team dynamics of globally distributed teams are also mentioned. We present the results and the extent to which the objectives were met. Finally, few challenges still faced by teams to move to shorter release cycle are highlighted.
收起
摘要 :
In medical imaging, the speed and reliability with which the data is transferred is crucial since it is life-critical. Data transfer should be robust to withstand bottlenecks so that images can be transferred reliably. This paper ...
展开
In medical imaging, the speed and reliability with which the data is transferred is crucial since it is life-critical. Data transfer should be robust to withstand bottlenecks so that images can be transferred reliably. This paper proposes a better approach to streamline the medical image transfer and to improve transfer performance across a DICOM network. Our study indicated that the performance of medical image transfer is lowered because of waiting for the responses and this delay attributed to 25-60 percent of total transfer time. The scope of this paper is to propose an approach to overcome the delay and to improve the performance of the medical image transfer.
收起
原文获取